home *** CD-ROM | disk | FTP | other *** search
/ kermit.columbia.edu / kermit.columbia.edu.tar / kermit.columbia.edu / newsgroups / misc.19950528-19950726 / 000409_news@columbia.edu_Sat Jul 22 15:33:32 1995.msg < prev    next >
Internet Message Format  |  1995-07-31  |  2KB
  1. Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA12442
  2.   (5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sat, 22 Jul 1995 16:23:34 -0400
  3. Received: by apakabar.cc.columbia.edu id AA03493
  4.   (5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sat, 22 Jul 1995 16:23:32 -0400
  5. Newsgroups: comp.protocols.kermit.misc
  6. Path: news.columbia.edu!sol.ctr.columbia.edu!news.moneng.mei.com!news.ecn.bgu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!spool.mu.edu!agate!library.ucla.edu!info.ucla.edu!csulb.edu!csus.edu!netcom.com!jhurwit
  7. From: jhurwit@netcom.com (Jeffrey Hurwit)
  8. Subject: Re: Kermit download from CompuServe.. best setup??
  9. Message-Id: <MpREww8Z7mxH084yn@netcom.com>
  10. Sender: jhurwit@netcom16.netcom.com
  11. Organization: Organization?  What organization?
  12. References: <3uidtu$r5c@hpber004.swiss.hp.com> <DC095G.Dp3@omen.com>
  13.  <3ulp8c$ep5@apakabar.cc.columbia.edu> <DC4Cr1.BB8@omen.com>
  14. Date: Sat, 22 Jul 1995 15:33:32 GMT
  15. Lines: 15
  16. Apparently-To: kermit.misc@watsun.cc.columbia.edu
  17.  
  18. In article <DC4Cr1.BB8@omen.com>, caf@omen.com (Chuck Forsberg WA7KGX) wrote:
  19.  
  20. >CompuServe claim they have not widely deployed ZMODEM because it
  21. >consumes too many resources.  I suspect CompuServe have made the
  22. >same measurements of system resources consumed by sz and Ckermit
  23. >and concluded that Ckermit is far more resource intensive than sz.
  24.  
  25.     I'm sure that a C-Kermit built with all the options is more
  26.     resource intensive, but then, that's because it does more. 
  27.     However, C-Kermit comes with a rich set of defines that permit it
  28.     to be installed without features that'll never be used.  In extreme
  29.     cases, it could be compiled with all but the protocol itself left
  30.     out (though I couldn't imagine leaving out the script interpreter!).
  31.  
  32.                                         Jeff